Overview
Identifying Business Needs
Reasons to Maintain a Single Domain
Ease of Management
Easier Delegation
Fewer Members in Domain Admins Group
Object Capacity Same as Multiple Domain Structure
Reasons to Create Multiple Domains
Reasons for Using a Multiple-Domain Tree:
Distinct domain-level policies
Tighter administrative control
Decentralized administration
Separation and control of affiliate relationships
Reduced replication traffic
Accessing Resources Between Domains
Authentication Across a Forest
Types of Trusts
Planning for Multiple-Domain Trees
Characteristics of Multiple-Domain Trees
Creating an Empty Root Domain
Design Guidelines
Design Needs that May Require a Multiple-Domain Tree:
Distinct Security Boundaries
Bandwidth Constraints on WAN Links
Legal Reasons for Separate Domains
Distinct Domain-Level Group Policy Settings
Planning for Multiple-Tree Forests
Characteristics of Multiple-Tree Forests
Design Guidelines
Consider Using a Multiple-Tree Forest When You Need:
Distinct DNS names for Public Identities
Centralized Control Among All Active Directory Trees and Domains
Planning for Multiple Forests
Characteristics of Multiple Forests
Design Guidelines
Design Multiple Forests When:
You Do Not Want a Common Schema
You Do Not Want a Global Directory
You Need Limited Partner or Affiliate Relationships